Meeting minutes
AvneeshSingh: it is the first call of this year!
Revision of User experience guide for displaying accessibility metadata.
<MURATA> +present
https://
AvneeshSingh: the main decision we made is that we should be focused more on how to interpret metadata and display
… less on the order of the metadata
… we may present some examples as inspiration for retailers and libraries
… then we had an editors' call where we decided to remove section 4, we decided to rewrite the rationale of the accessibility summary
… there was also a need to group the metadata in headings, so the structure of the document becomes more readable
https://
AvneeshSingh: George has already updated the rationale of the accesibility Summary
https://
AvneeshSingh: Gregorio has reorganized the principles' document
CharlesL: we're trying to say that the accessibility summary should not be a duplicate of other machine readable metadata, so to use this field for adding information that cannot be expressed with machine readable metdata
AvneeshSingh: we'll keep this editorial changes by 5 days, if we don't get feedback we'll merge it
… We also discuss to group metadata and to move the definition to the group
gpellegrino: worked with Gautier, list all EPUB metadata and list all the ONIX code, its not a mapping, and list what are the requirements of the EU A11Y Act.
… , proposed some grouping of metadata, Reading Mode and suggested some values (visual adjustments, audio, etc.)
<Bill_Kasdorf> could you put the link to this Google Sheet in the IRC or chat, please? It's terrific!
gpellegrino: , these are only proposals, lets figure out the groupings, reading mode, navigation, book features (mathml, long desc etc.), certification, compliance
… , 7 groups so far, and some metadata may not be specific to a11y , is this a reflowable, drm, fixed layout etc. Not in the a11y metadata but in the main section list these in UX guidelines display this info in the page about the product price/title etc.
https://
<Bill_Kasdorf> you could just provide view permission, not edit. But thanks!
AvneeshSingh: grouping these in the UX guide and more logical structure.
@Bill_Kasdorf: updated!
George: guidance on the format, not part of the a11y metadata. I like. category names, audio book, pdf, fixed layout, media overlays and any of these main stream domains (DAISY 3/2 Megavoice could be considered, BRF eBRF etc.
gpellegrino: currently the google doc is read only
gpellegrino: what is missing is just consensus on the grid then we can move to the document.
laurent_: I agree the grouping is good, when it comes to the UI and order, be careful to mapping to UI order, empty groups having one set of info that is always displayed main info, and display others that contain information so we don't get a lot of empty groups.
gpellegrino: I agree with laurent_, in this spreadsheet I listed all metadata, some metadata will never appear or in few cases. Eg. tactile graphic etc. Some real cases most used metadata real feel of what may be displayed.
Hadrien: At deMark we have a11y feature in two products, approach taken, primary metadata, and secondary. product page and some while browsing, and the others are not displayed you must do something to see it all, and the 3rd items we don't display too complex.
… , primary Conforms to WCAG AA, secondary is a11y features/hazards, and 3rd are access modes that are complex or features that are very uncommon.
AvneeshSingh: this is great and we should show this in some examples.
… , google spreadsheet - move forward on grouping this on a github issue and come back to this on our next call. could finalized on next call.
https://
Accessibility summary authoring guide is available for review:
AvneeshSingh: we're trying to invite other groups that are working on metadata display
https://
AvneeshSingh: the summary authoring guide is open for feedback
CharlesL: I think that we may close the feedback window in one month
… maybe would be useful to have some real world examples
GeorgeK: if someone wants to add examples, is more than welcome
CharlesL: do we have a GitHub issue for accessibility summary feedback?
https://
https://
AvneeshSingh: in the first call of February we can finalize it
Any other business.
CharlesL: Pagebreak: the issue was that we have printPageMumbers accessibility feature
… when you use it, you have to put the source of the page source using the dc:source metadata
… but in some cases we have paginated publications which are not prinnted
… so we're adding a new feature called pageMarkes
… and another for pageNavigation (you can navigate by pages using the pagelist)
… and we're defining a new metadata element for defining the page source for pagination
… we're trying to simplify things
CharlesL: we can add values in the accessibility features' list
AvneeshSingh: this changes cannot fit in version 1.1, we're experimenting for the new version
matt: eventually we can update the techniques
laurent_: I think this feature is not important only for accessibility, but for everyone experience
CharlesL: GCA we'll push this new version to all publishers that are part of the program
AvneeshSingh: good point Laurent