[en] Button Pattern - Feedback from APG List

[lolaodelola]

"Hi W3C organization

I am working and researching about web accessibility for 4 years now. I would like to inform you guys that there are no direct indication about button look or appearance. Default buttons styles are not followed by almost all origination. Buttons are very essential for everyday users and strongly focusing on that will be my humble request. I would strongly expect a improvement following the list down below -

• Buttons should have some indication that it's a button
• Indication of button or the border should have minimum contract ratio, I will suggest same for the link underline.
• Only use of color shouldn't be acceptable if it doesn't pass the minimum contract ratio.

I would love to see changes made for this purpose and if not I will request to have a explanation about that for my learning development. I can provide explaination for my request requirements if needed."

[css-meeting-bot]

The ARIA Authoring Practices (APG) Task Force just discussed Issue 3153 - Request for design requirements in button pattern.

The full IRC log of that discussion

<jugglinmike> Topic: Issue 3153 - Request for design requirements in button pattern
<jugglinmike> github: https://github.com/w3c/aria-practices/issues/3153
<jugglinmike> Matt_King: The way I interpret this is that this person would like us to provide visual design guidance for buttons
<jugglinmike> Matt_King: This feels to me like it could be outside of the scope of the APG
<jugglinmike> Jem: It could be WCAG...
<jugglinmike> Jem: Are they asking us to change the button design?
<jugglinmike> Matt_King: No, I think they want an additoin to the button pattern. They say that button should have some indication that it is a button. Also that it has a minimum contrast ratio (which is obviously WCAG)
<jugglinmike> Matt_King: In the introduction to the APG, we have a "purpose" section...
<siri> +q
<jugglinmike> https://www.w3.org/WAI/ARIA/apg/about/introduction/
<jugglinmike> Matt_King: We do not explicitly say that the APG is not about giving guidance on the visual experience. However, we don't do that for any other patterns. It doesn't feel like the job of the APG
<jugglinmike> Matt_King: Maybe that represents an omission in the definition of our scope
<Jem> "APG is not a UI Design System"
<Jem> https://www.w3.org/WAI/ARIA/apg/about/introduction/
<jugglinmike> siri: All of the criteria they have requested are WCAG requirement
<jugglinmike> Matt_King: We make sure that everything we do is consistent with WCAG
<jugglinmike> siri: I don't think we did this for other examples, either
<jugglinmike> Jem: I think it's enough that the introduction says that "APG is not a UI Design System"
<jugglinmike> Matt_King: Our job is not to be a WCAG explainer. WCAG explains WCAG
<jugglinmike> Matt_King: Maybe we cover it in the prerequisite knowledge
<jugglinmike> Matt_King: I'm going to close this unless anyone objects
<jugglinmike> [no objections]
<jugglinmike> Zakim, end the meeting

[mcking65]

Closing as won't fix.

To summarize the APG task force position on this issue, the task force considers providing basic accessible visual design guidance for the patterns to be outside the scope of the APG. Visual design guidance is included in the APG only in cases where visual design considerations are a necessary element of an in-scope APG objective and are not provided by another W3C resource that can be referenced by the APG.

The reasoning for this position is partially explained in the Important Prerequisite Knowledge section of the APG Intorduction, which says in part:

some important aspects of creating accessible experiences fall outside the scope of the APG. This section describes the types of prerequisite knowledge and supporting resources that may enable readers to derive maximum benefit from the APG.

@lolaodelola please reply to the email thread with this answer.