Meeting minutes
Sec 2.4: PDF https://a11yedge.github.io/capabilities/#pdf
Lionel_Wolberger: remove ' incorrect reading order' from the automatability section.
… may want to remove the reference to why we are doing this (... people with assistive tech)
Chris: There should be a way to make short reference to this as it recurs
Sec 3.2.2: Provide Dyslexia Friendly Fonts https://a11yedge.github.io/capabilities/#dyslexiafont
Lionel_Wolberger: For the list on increased height etc, preface it by saying 'for example'
… benefit is too assertive. It needs to be lightened, e.g., add 'for many users'
… Using dyslexia-friendly fonts can reduce cognitive load for some people with dyslexia
… delete ', prioritizing aesthetics over readability.'
… change 'However, full integration with existing styles and design systems requires manual adjustments.' to 'However, invocation requires manual adjustment or decision-making.'
shaun: The automatability sections are standardized now with m-dash
<Lionel_Wolberger> +1
Sec 3.2.3: Accessible Pricing https://a11yedge.github.io/capabilities/#pricing
<shaun> "About Automatability - In many cases — Suggesting that automation can successfully remediate and verify outcomes across a broad set of websites.
<shaun> In some cases — Pointing to potential success in specific implementations where the variables, website structures and code are well-understood and controlled.
<shaun> In no significant way — Indicating scenarios where current automation strategies are unlikely to be effective without significant human oversight.
<shaun> Does Not Apply—Is sometimes indicated for completeness.
Jason: The source heading is a place to discuss why source sometimes is not sufficient.
… or point to the habits of source that end up demanding post-source adaptation
… it is not just a statement of why source is the best place for everything. That is front-loaded and clear, that source is a good place to get it done
… Janina, note -- add this explanatory note to the introduction on the source, trade-offs overview
… 1.4 in the intro
Sec 3.4: Color https://a11yedge.github.io/capabilities/#color
janina: I will merge this 3.4 for reading next week.
Sec 3.4: Color https://a11yedge.github.io/capabilities/#color
Lionel_Wolberger: Colors are inherently adjustable via CSS, so color palettes could be determined by end users.
Lionel_Wolberger: Lionel review section 3.4 for accuracy by next week
Sec 3.5: Page Styling https://a11yedge.github.io/capabilities/#pagestyling
Lionel_Wolberger: The headings need 'blabla' under each one, I will supply
Jason: 3.5.2, source does not show how it can get it wrong
… add, the concern for the source design may override the need for distinguishable text boxes and borders
janina: Talking about blabla-- we plan a pass to link to WCAG, which will have comprehensive blabla
Lionel_Wolberger: on the source of shadow fonts, add something like the above:
… .. the source's design may override the need for shadow and other effects that are distinguishable by people of all abilities
Lionel_Wolberger: 3.5.4 add to source, 'such effects generally violate WCAG color contrast minimums.
Sec 4.2: Custom Components https://a11yedge.github.io/capabilities/#custcomponent
Shaun: Which is tradeoff? Is it TradeOffs, Trade-offs, or Trade Offs?
janina: Decision: Trade-Off as it is title case
<shaun> Claude confirms Trade-Offs when used as a title.
Lionel_Wolberger: The W3C community divides components into two types: standard components and non-standard components
<shaun> Apologies, I have to go pick up my daughter.
Lionel: This is a list from my work: Tab panels, accordions, menu bars, tree widget, combo box, list box, multi-select list box, alert dialog, alerts, carousel sliders
jason: This non-standard list is the type of component we are dealing with in this section
… I know the term 'interactive components'
https://
Lionel_Wolberger: Standard components are Anchors, buttons, form fields
janina: WAI calls it custom controls
Lionel_Wolberger: Not sure a control is a component
jason: For 4.2.2, delete the first source/trade-offs/benefits/auto section, keep the second.
Third Party Risk
Chris: Are some post-source remediations done by a third party?
Lionel_Wolberger: Yes
Chris: Law firms are overt about the caliber of any third parties, particularly from the standpoint of security\
… 3rd parties bring in supply chain type issues
… for a 3rd party to enter, implies that new risks could be introduced
… justt like food provenance, the document should address the provenance and risk issues that come from having multiple 3rd parties mash-up into a single page