W3C

PM WG A11y Task Force Call

29 May 2025

Attendees

Present
AvneeshSingh, George, Madeleine5, mgarrish
Regrets
-
Chair
AvneeshSingh
Scribe
mgarrish

Meeting minutes

Implementation details of EPUB metadata for publisher contact.

<AvneeshSingh> w3c/epub-specs#2702

AvneeshSingh: should we be using role or another dedicated metadata

mgarrish: I'd go with minting our own new property - using refines is too complicated

AvneeshSingh: agree

Decision on AccessmodeSufficient.

<AvneeshSingh> w3c/epub-specs#2679

RESOLUTION: add properties for publisher and trusted intermediary contacts

mgarrish: it's problematic to reduce requirements in new standards as it makes it incompatible with older versions

George: maybe we should only make access mode sufficient required

Madeleine5: access mode sufficient is the most complicated to understand

George: it's repeatable but we allow textual and visual as single statements

AvneeshSingh: can this be automated

Madeleine5: yes, I've automated these in the past to make access modes from other metadata

AvneeshSingh: daisy pipeline computes metadata when it compiles an epub - but need to check if it works with edge cases

AvneeshSingh: we could bump it up to mandatory and see if people resist

Madeleine5: so we want compatibility with previous

mgarrish: content doesn't break if we change the conformance identifier

AvneeshSingh: let's update the tracker that we're going to move it to a requirement and if we don't get any negative feedback after a couple of weeks we can move it to the spec

Creation of a common document for explaining the accessibility metadata.

w3c/publ-a11y#723

mgarrish: consolidates all the information about the accessibility metadata that was spread around in different documents and consolidates it into a single new guide that we'll maintain

George: is this rec track?

mgarrish: no, this will be maintained by the CG

upgrading the floor WCAG specification for EPUB Accessibility 1.1.x from WCAG 2.0 to 2.2.

<AvneeshSingh> w3c/epub-specs#2717

AvneeshSingh: should we elevate the floor from WCAG 2.0 level A
… there is no urgency to make this change - WCAG 2 versions do not supersede each other

mgarrish: what about raising just the level?

AvneeshSingh: could be problematic as some regions still only require level A

AvneeshSingh: let's continue with the status quo and see if we get any other feedback

Next meeting on June 19.

Summary of resolutions

  1. add properties for publisher and trusted intermediary contacts
Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).