Re: Call for Consensus, send 4 rules to working group for approval

Hey Shunguo,
Thank you for reviewing these rules. Let's discuss this during this
Thursday's meeting.

On Tue, Feb 11, 2025 at 5:51 PM Shunguo Yan <shunguoy@us.ibm.com> wrote:

> Hi Kathy,
>
>       I have a couple of suggestions for the two rules for approval:
>
>
>
>    1.  The rule  *Summary element has non-empty accessible name
>    <https://www.w3.org/WAI/standards-guidelines/act/rules/2t702h/proposed/>*
>
> Based on HTML5
> <https://html.spec.whatwg.org/multipage/interactive-elements.html#the-summary-element>,
>  The <summary> is only used as the first child of a <detail> element.  In
> other words, if a <summary> is not used as the first child of a <detail>,
> it’s invalid.  The use of <summary> in the Passed Examples 4 & 5, and
> Failed example 3 are in question.  The HTML violations can be tested in
> w3c’s Markup Validation service <https://validator.w3.org/>.   ACT test
> cases should only use valid HTML examples.
>
>
>
>    2. The rule *ARIA required owned elements
>    <https://www.w3.org/WAI/standards-guidelines/act/rules/bc4a75/proposed/>*
>
> The Inapplicable example 1:  <ul><li>item 1</li></ul>.  This should be a
> Passed example.  The implicit roles for <ul> and <li> are ‘list’ and
> ‘listitem’, and the owned element relationship is satisfied in the
> example.  Whether an element has an explicit role or not shouldn’t be the
> “inapplicable” condition.
>
> The Passed examples 3 & 4: <li role=’none’></li>.  Based on Aria in HTML
> <https://www.w3.org/TR/html-aria/>, the role “none” is invalid for the
> <li>.  Suggest changing to something else, like <div role=’none’></div> to
> make the Passed example valid.
>
>
>
> Regards,
>
>
>
> Shunguo Yan, Ph.D.
>
> Accessibility Technology & Innovation
>
>
>
>
>
>
>
> *From: *Katherine Eng <eng@access-board.gov>
> *Date: *Monday, February 10, 2025 at 4:54 PM
> *To: *ACT Task Force (Only) <public-wcag-act@w3.org>
> *Subject: *[EXTERNAL] Call for Consensus, send 4 rules to working group
> for approval
>
> Hi everyone, We think the following rules are ready for approval and
> publication: Summary element has non-empty accessible name ARIA required
> owned elements Although these two rules have already been through CFC and
> approved (in March 2024),
>
> Hi everyone,
>
>
>
> We think the following rules are ready for approval and publication:
>
>
>
>    1. *Summary element has non-empty accessible name
>    <https://www.w3.org/WAI/standards-guidelines/act/rules/2t702h/proposed/>*
>    2. *ARIA required owned elements
>    <https://www.w3.org/WAI/standards-guidelines/act/rules/bc4a75/proposed/>*
>
>
>
> Although these two rules have already been through CFC and approved (in
> March 2024), it’s been a while so please take another look:
>
>    3. *Element with role attribute has required states and properties
>    <https://www.w3.org/WAI/standards-guidelines/act/rules/4e8ab6/proposed/>*
>    4. *Orientation of the page is not restricted using CSS transforms
>    <https://www.w3.org/WAI/standards-guidelines/act/rules/b33eff/proposed/>*
>
>
>
> Please respond with +1 if you support requesting approval to publish these
> 4 rules or -1 if you oppose. Call for Consensus ends Feb 24.
>
>
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Kathy Eng
>
> Senior ICT Accessibility Specialist
>
> U.S. Access Board <https://www.access-board.gov/ict>
>
>
>
> *[image: U.S. Access Board logo]*
>
>
>
> Visit our website and sign up for one of our free webinars
> <https://www.access-board.gov/webinars/>.
>
>
>


-- 
*Wilco Fiers*
Principal product owner - W3C AC Rep - Facilitator ACT Task Force