Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposed definition for Inactive #1154

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Proposed definition for Inactive #1154

Show file tree
Hide file tree
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
27db111
Proposed definition for Inactive
Jun 9, 2020
8e2df4f
adjusted for Chuck's comment
Jun 10, 2020
e172c3e
adding definition link for inactive
Jun 11, 2020
c380ee6
Adding definition link for inactive
Jun 11, 2020
a41c965
Adding link to definition for inactive
Jun 11, 2020
1a2427d
Adding read-only input note.
alastc Jun 16, 2020
ab5b722
switched present for visible.
alastc Jun 16, 2020
ddf8f07
Merge branch 'main' into WCAG22_inactive_def
patrickhlauke Oct 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions guidelines/sc/20/contrast-enhanced.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ <h4>Contrast (Enhanced)</h4>

<dd>

<p>Text or images of text that are part of an inactive <a>user interface component</a>, that are <a>pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant
<p>Text or images of text that are part of an <a>inactive</a> <a>user interface component</a>, that are <a>pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant
other visual content, have no contrast requirement.
</p>

Expand All @@ -38,4 +38,4 @@ <h4>Contrast (Enhanced)</h4>

</dl>

</section>
</section>
4 changes: 2 additions & 2 deletions guidelines/sc/20/contrast-minimum.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ <h4>Contrast (Minimum)</h4>

<dd>

<p>Text or images of text that are part of an inactive <a>user interface component</a>, that are <a>pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant
<p>Text or images of text that are part of an <a>inactive</a> <a>user interface component</a>, that are <a>pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant
other visual content, have no contrast requirement.
</p>

Expand All @@ -38,4 +38,4 @@ <h4>Contrast (Minimum)</h4>

</dl>

</section>
</section>
2 changes: 1 addition & 1 deletion guidelines/sc/21/non-text-contrast.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ <h4>Non-text Contrast</h4>

<dt>User Interface Components</dt>

<dd>Visual information required to identify <a>user interface components</a> and <a>states</a>, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;</dd>
<dd>Visual information required to identify <a>user interface components</a> and <a>states</a>, except for <a>inactive</a> components or where the appearance of the component is determined by the user agent and not modified by the author;</dd>

<dt>Graphical Objects</dt>

Expand Down
8 changes: 8 additions & 0 deletions guidelines/terms/22/inactive.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
<dt><dfn>inactive</dfn> (user interface components)</dt>
<dd class="new">
<p class="change">New</p>
<p>A state of a <a>User Interface Component</a> when it is not available for user interaction, such as a disabled control in HTML. An inactive user interface component is present but not currently operable using standard input mechanisms such as keyboard, pointer, or assistive technology.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about?

Suggested change
<p>A state of a <a>User Interface Component</a> when it is not available for user interaction, such as a disabled control in HTML. An inactive user interface component is present but not currently operable using standard input mechanisms such as keyboard, pointer, or assistive technology.</p>
<p>A state of a <a>User Interface Component</a> when it is not available for user interaction, such as a disabled control in HTML. An inactive user interface component is present, and in some cases may even be focusable, but is not currently operable using standard input mechanisms such as keyboard, pointer, or assistive technology.</p>

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd still say that this is unnecessary, but can live with it...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, I think this is marring the definition of inactive, which I think is both inoperable AND not navigable.

Suggested change
<p>A state of a <a>User Interface Component</a> when it is not available for user interaction, such as a disabled control in HTML. An inactive user interface component is present but not currently operable using standard input mechanisms such as keyboard, pointer, or assistive technology.</p>
<p>A state of a <a>User Interface Component</a> when it is not available for user interaction, such as a disabled control in HTML. An inactive user interface component is present but not currently operable or navigable using standard input mechanisms such as keyboard, pointer, or assistive technology.</p>

<p class="note">An example inactive user interface component is a submit button at the bottom of a form which is present but cannot be activated until all the required fields in the form are completed.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about controls that take focus but cannot be activated such as a date in a grid which is not available or the other control types specified at https://w3c.github.io/aria-practices/#kbd_disabled_controls.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think that's covered by the proposed definition there, since it says nothing about whether or not the inactive component can receive focus or not...just that it's not available for user interaction (unless you mean that even the act of focusing on it is an interaction?) / operable.

Copy link
Member

@jnurthen jnurthen Mar 3, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes IMO focusing is an interaction so this doesn't apply if focusable as written

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That wording from the APG really complicates things. I'm inclined to say that if something is navigable but not operable, it should not be considered disabled (and should not be given a pass on text contrast considerations). We spent a lot of time at IBM designing read-only versions of components; it was difficult, but it is possible. There should be a way of achieving minimum contrast for unavailable options in a listbox (to use one of the APG examples), if the desire is to make them discoverable by all. Letting them be 'discoverable' programmatically but not visually seems inequitable.

<p class="note">An inactive user interface component should not be confused with controls which are not currently selected. For example in a tabbed interface, the tabs which are not selected are not regarded as inactive user interface components - they may be interacted with by the user to switch tabs in the tabbed interface, and therefore do not meet the definition of inactive.</p>
<p class="note>A read-only text input field which is focusable using standard input mechanisms is considered to be active.</p>
</dd>