Provide feedback on ARIA issues filed to address issues raised during this workshop

[joanmarie]

One possible approach to some of the issues discussed during this workshop may be adding one or more attributes in ARIA. In order for the ARIA Working Group to better understand the need and reach consensus on where/how this need should be addressed, it will need more information.

Some issues I've filed or which seem relevant include:

• Consider adding context attribute through which ATs could ensure correct presentation of content w3c/aria#767
• Consider addition of property(ies) to expose braille string w3c/aria#765
• Adding roles, states, and properties to support math w3c/aria#660
• Propose new attribute for SSML to provide pronunciation or presentational hinting to AT w3c/aria#659

Others are expected to be filed. I think it would be great if we could collect those here to ensure workshop members are able to quickly find them and provide their input.

[sinabahram]

I've linked a page below that we're working on as part of the development going on this week. It exemplifies the custom Braille output, raw Braille input, and math in live regions use cases with html coded against these imaginary attributes purely for purposes of prototyping.

https://sinabahram.github.io/aria-playground/

[rbeezer]

• Landmark Region Guidance: navigation in banner w3c/aria-practices#692
• "Step 3" of Authoring Practices w3c/aria-practices#690
• Landmark region guidance: sub-regions for document sections? w3c/aria-practices#691

[joanmarie]

Also: w3c/aria-practices#696 (Consider adding guidance related to including interactive objects and MathML in live regions)

[samdooley]

Also: w3c/aria#771 re untranslated Braille input