Minutes: April 27, 2016 SVG Accessibility Task Force Meeting

http://www.w3.org/2016/04/27-svg-a11y-minutes.html <http://www.w3.org/2016/04/27-svg-a11y-minutes.html>

Text:

Topics <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#agenda>
Any news or things to add to the agenda <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#item01>
Authoring Document <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#item02>
Last Meeting’s resolution <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#item03>
Action 2044 <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#item04>
Action 2021 <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#item05>
default native host language semantics for the SVG element and how to process <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#item06>
How should we in the graphics module give a preview for a more complex set of graphics roles in the future? <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#item07>
Summary of Action Items <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#ActionSummary>
Summary of Resolutions <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#ResolutionSummary>


<scribe> scribe: Rich

Any news or things to add to the agenda

<fesch> https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0030.html <https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0030.html>
<fesch> https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0029.html <https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0029.html>
Authoring Document

Doug: Charles and I met a couple weeks ago and we talked about the structure.
... I am working on a new outline over the old one
... I am going to put it in the SVG repository
... I chatted with Fred about it and he pointed me to authoring guidance for ARIA.
... I suggested it was not the right format for ours
... It might be appropriate for data visualization later
... I will be sharing a link to a github repo. for it
... I would like to put this on the agenda for next week and I would like people to review it.

Fred: Who can edit it?

<chaals> chaals: I can.

Doug: I want to do it all with pull requests
... I can take email

Amelia: it provides lasting documentation and discussions related to it

Fred: can you send out an email notification ahead of time?

Doug: yes

Last Meeting’s resolution

Fred: this is child vs. descendant

<fesch> Where an element has role=none or role=presentation and has a

<fesch> descendent title or desc element, user agents must ignore the role.

<fesch> https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0014.html <https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0014.html>
<fesch> https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0016.html <https://lists.w3.org/Archives/Public/public-svg-a11y/2016Apr/0016.html>
Fred: This should say that it has s child title or desc

Amelia: yes

RESOLUTION: Just fix it treating it as a typo

Amelia: your email of April 12th ...

<AmeliaBR> Corrected resolution text would be: Where an element has role=none or role=presentation and has a direct child title or desc element, user agents must ignore the role.

+11

Fred: I will let Joanie I corrected our typo

RESOLUTION: Where an element has role=none or role=presentation and has a direct child title or desc element, user agents must ignore the role

Fred: Originally, I wanted role presentation and none to be like a gold hammer where the person would know it would not show up in the accessibility tree
... That did not work due to exceptions like adding a tabindex

Action 2044

https://rawgit.com/w3c/aria/action2044/aria/aria.html#override_presentation_none <https://rawgit.com/w3c/aria/action2044/aria/aria.html#override_presentation_none>
Rich: I will be looking for comments from Amelia and other on this over the next week

Action 2021

<fesch> Action-2021

<trackbot> Action-2021 -- Richard Schwerdtfeger to Work role=none/presentation into ARIA spec -- due 2016-04-20 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2021 <http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2021>
<AmeliaBR> Discussion here: https://github.com/w3c/aria/issues/347 <https://github.com/w3c/aria/issues/347>
default native host language semantics for the SVG element and how to process

https://github.com/w3c/aria/issues/347 <https://github.com/w3c/aria/issues/347>
Rich: What do we do if it is empty?

Amelia: it is empty in terms of the accessibility tree such as a uniform image
... We don’t want to map it to group in the long run
... Group does not make sense
... The mappings will be in the be in the graphics-aam
... the SVG mapping spec. will refer to the graphics-aam

Rich: Steve Faulkner has said HTML needs to point to the SVG specification for the <SVG> element
... I am speaking to Joanie about the mappings

 <><scribe> ACTION: Amelia update the SVG AAM and SVG2 to use the new graphics roles [recorded in http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action01] <http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action01]>
<trackbot> Created ACTION-2022 - Update the svg aam and svg2 to use the new graphics roles [on Amelia Bellamy-Royds - due 2016-05-04].

Rich: We need to lock down SVG2, HTML 5.1, ARIA 1.1, and the Graphics ARIA module first and then the AAM shall follow

Amelia: We need to have agreement on the ARIA role mappings and the AAMs will expose them

Fred: On the github issue then I guess we go ahead report that we are moving graphics group to graphics document - defer to SVG for SVG related semantics and mappings
... Leonie, was there any contention to graphics docs not having children?

RESOLUTION: No issues with switching to using graphics-doc over the ARIA group role
... No issues with graphics-doc not having children

How should we in the graphics module give a preview for a more complex set of graphics roles in the future?

Fred: Judy asked for the status of this
... I talked about the basic plumbing being taken care consistently first
... Any issues with putting this in the inroduction

<AmeliaBR> This specification defines the core roles that would be used in all structured graphics or diagrams. Future work will expand on this framework to enable more detailed annotation of data-rich graphics such as charts or maps.

<AmeliaBR> (Those are relevant comments from current spec text.)

Rich: The intent of this specification is to work in harmony with SVG2 and ARIA 1.1 to get consistent working accessibility infrastructure, on par with WAI-ARIA and HTML5.1, across all the major browsers.

The intent of this specification is to work in harmony with SVG2 and ARIA 1.1 to get consistent working accessibility infrastructure and keyboard support, on par with WAI-ARIA and HTML5.1, across all the major browsers.

 <><scribe> ACTION: Fred make changes to the Introduction regarding this release of the graphics module and future releases [recorded in http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action02] <http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action02]>
<trackbot> Created ACTION-2023 - Make changes to the introduction regarding this release of the graphics module and future releases [on Fred Esch - due 2016-05-04].

Summary of Action Items <>[NEW] ACTION: Amelia update the SVG AAM and SVG2 to use the new graphics roles [recorded in http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action01 <http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action01>]
[NEW] ACTION: Fred make changes to the Introduction regarding this release of the graphics module and future releases [recorded in http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action02 <http://www.w3.org/2016/04/27-svg-a11y-minutes.html#action02>]
 
Summary of Resolutions <>
Just fix it treating it as a typo <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#resolution01>
Where an element has role=none or role=presentation and has a direct child title or desc element, user agents must ignore the role <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#resolution02>
No issues with switching to using graphics-doc over the ARIA group role <https://www.w3.org/2016/04/27-svg-a11y-minutes.html#resolution03>[End of minutes]



Rich Schwerdtfeger