– DRAFT –
(MEETING TITLE)

Approval for publishing of the AccessibilitySummary authoring guide.

<AvneeshSingh> https://w3c.github.io/publ-a11y/drafts/schema-a11y-summary/index.html

George: For me it's done. Next revision we would make a lot of changes, for now its ready. I implemented everything that was asked for.

AvneeshSingh: will implement the revisions from Gregorio.

<AvneeshSingh> proposed: approve accessibility summary authoring guide for publishing as CG report

<gpellegrino> +1

+1

<GeorgeK> +1

<JonasL> +1

<JF> +1

<AvneeshSingh> resolved

Next steps for revision of User experience guide. We should focus on refactoring section 4.

<AvneeshSingh> https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/

AvneeshSingh: We ultimately need to add this to the Principles document.
… we should not try to achieve perfection, and move this over as soon as possible.

<AvneeshSingh> https://docs.google.com/spreadsheets/d/1rUCXkVE0bFeXf0hJvyPkKkIBeBHIGPYUFWKrQqLJHl8/edit?usp=sharing

AvneeshSingh: to Github.

<AvneeshSingh> w3c/publ-a11y#148

ISSUE: merging "Reading Mode: Audio" and "Reading Mode: Non visual"?

AvneeshSingh: We just need to come up with a name but can refine it later if needed.

gpellegrino: One for reading mode audio and one for reading mode visual.
… non visual reading mode means using AT
… there was a proposal for coming up with a name for each.

AvneeshSingh: issue tracker I proposed an explainer sentence: "enable reading without sight".
… we can always change in the future.

gpellegrino: its fine for me.
… row 12 to row 15, and row 20-23
… non visual 12-15 then reading mode audio 20-23

12-15: accessModeSufficient = textual

accessibilityFeature = ttsMarkup

accessibilityFeature = readingOrder

accessibilityFeature = alternativeText

20-23: accessModeSufficient = auditory

accessibilityFeature = synchronizedAudioText

accessibilityFeature = highContrastAudio

accessibilityFeature = audioDescription

AvneeshSingh: this is just a placeholder for now.

GeorgeK: Matt & I wrote this modes of reading and can redo to make this in line with this.

<AvneeshSingh> w3c/publ-a11y#155

<gpellegrino> w3c/publ-a11y#155

AvneeshSingh: resolved.

gpellegrino: we missed accessMode, we need to add it.

<JF> +1 for completion sake

AvneeshSingh: for completion we should add it to the spreadsheet. just where will it go.

gpellegrino: just identifies that a mode is present.

<AvneeshSingh> w3c/publ-a11y#156

AvneeshSingh: Gregorio please suggest an idea in github and we can comment.

gpellegrino: ok
… Books features: proposal subgroups for those book features. like what we are doing for Reading mode.
… • Structure and Navigation Terms

• Adaptation Terms

• Rendering Control Terms

• Specialized Markup Terms

• Clarity Terms

• Tactile Terms

• none
… we can leave this open for discussion. maybe we can think about it later.

AvneeshSingh: Yes, move these decisions to the User Experience guide and these subgrouping can be done and refined.

<gpellegrino> w3c/publ-a11y#157

gpellegrino: missing metadata - some a11y features and hazards and should add them.
… • accessibilityFeature = pageBreakMarkers (perhaps the pagination source should be included as well?)

• accessibilityHazard = noFlashingHazard

• accessibilityHazard = noMotionSimulationHazard

• accessibilityHazard = noSoundHazard

• accessibilityHazard = unknown

AvneeshSingh: approved.

AvneeshSingh: Huge list of metadata would be good to chunk it up into smaller pieces.

gpellegrino: 1 group at a time?

<gpellegrino> +1 to avneesh proposal

AvneeshSingh: put in all these new groupings, new descriptions, put only the names of categories and items and then add the descriptions later.

Bill_Kasdorf: always tempting to put in tabular fashion, and not use tables but use lists instead in the guide.

AvneeshSingh: put all categories as headings and list of all metadata and then add the description, managing overload of info will be the tangent.

GeorgeK: principles needed to be updated we also in techniques we will have opportunities of translations like "Screen Reader Friendly" will principles on which docs to read next? Or put a lot of that detail in principles. ie. how will we divide it up?

Charles: maybe have a language option and then can go to the various techniques documents in another language and those terms would be in that language. so if Screen Reader Friendly is not good for another language then that would be defined for that language.

JF: WAI documents Shawn should be coordinated for any translations. maybe invite to one of our calls. Who will do the translations.

<Bill_Kasdorf> We could never provide all the translations necessary.

AvneeshSingh: We are not planning to translate, we will create a structure to facilitate that can be translated. like EDRLab. we will discuss this with Shawn. we will have this framework in place.

JF: Agreed include Shawn is well advised here.

<Bill_Kasdorf> +1 to George

GeorgeK: the focus on what we want to translate is the user facing information. to describe the features , access modes etc. we are just translating very short phrases. I don't think we should translate into all languages just the user facing descriptions.

gpellegrino: localization of the strings not the actual text of the document.

AvneeshSingh: editors should have a call, put forth a plan and present to this group.

+1

<JF> +1 to Avneesh's plan

Any other business.

AvneeshSingh: Agreed.

AvneeshSingh: I will have a conflict for this time-slot on other W3C commitments.
… can we use a doodle poll is that accessible now? is there another version.

GeorgeK: wendy says its broken.
… Charles and I have a biweekly call, if we could set it up after this at say 15:00 UTC that would work for Charles and I

JF: I am flexible on time.

<Bill_Kasdorf> +1

<Chris> +1

AvneeshSingh: 15:00 UTC / 11 Boston. anyone conflicts… none ok. resolved

<AvneeshSingh> we will have calls at 15 UTC, on same days

JF: conformance statement
… want guidance on how to do that we can declare in metadata that a conformance statement exists like URL.
… Is there a standardize format. are we using VPAT

GeorgeK: this is regarding a Conformance Report not Conformance Statement ie. conformsTo

JF: everyone is doing whatever they want.
… its often the same players. I have been trying to get an answer to if we are looking for new work. what we mean / expect.
… I would like to do this at the book level. We are working on a remediation tool and can export a certifier report
… if LIA is blazing the trail maybe we should look like they are doing and we like it then thats one step closer to a standardized report.

gpellegrino: the URL on our server which has a page on our server I can send a link John. Cover, title, with the accessibility features, and just to inform that it is certified by us or not.

AvneeshSingh: can you check Gregorio to LIA is ok to share with this group.

JF: I thought the certifier report was a lot more granular, and has the WCAG + the EPUB specific. we are working towards GCA certifiction, and must meet all the WCAG.

AvneeshSingh: the purpose is validation so a reader can validate the claim is correct, but you may be using for providing the details of conformance.

JF: my understanding is different than what LIA's interpretation.

AvneeshSingh: both are correct.
… please open an issue then we can work on it through github.

JF: Ok I will open an issue.

AvneeshSingh: I can do that and send the link to the mailing list so we can discuss it there. use it as verification / detailed report
… SMART report is an option

Bill: what Gregorio is certifying is an individual book, vs GCA is certifying a a publisher/vendor pipeline
… VPAT is slightly different again on this date this is the state of a11y at that point in time.

JF: if we have GCA then books are compliant. I know there may not be 100% but GCA has that 80%, EPUB is a collection of web pages we should be able to do a dated VPAT for individual publications. is it hosted on a third party server we can point to it … concerns about pointing to a server.
… need more precise I think we need this and maybe even in WCAG 3. lots of all challenges.

AvneeshSingh: I will open the issue then folks can comment
… we will have our next meeting at the new time.