-
Notifications
You must be signed in to change notification settings - Fork 125
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.
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
Editorial: Update computation step "comp_embedded_control" (formerly step 2c) text for clarity #2299
base: main
Are you sure you want to change the base?
Editorial: Update computation step "comp_embedded_control" (formerly step 2c) text for clarity #2299
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -554,9 +554,8 @@ <h4>Computation steps</h4> | |||||
</div> | ||||||
</li> | ||||||
<li id="comp_embedded_control"> | ||||||
<span id="step2C"><!-- Don't link to this legacy numbered ID. --></span><em>Embedded Control:</em> Otherwise, if the <code>current node</code> is a control embedded within the label | ||||||
(e.g. any element directly referenced by <code>aria-labelledby</code>) for another <a class="termref">widget</a>, where the user can adjust the embedded control's value, then return | ||||||
the embedded control as part of the text alternative in the following manner: | ||||||
<span id="step2C"><!-- Don't link to this legacy numbered ID. --></span><em>Embedded Control:</em> Otherwise, if the <code>current node</code> is a user-adjustable control embedded | ||||||
within the label, and the control is not the element being named or described, then return the embedded control's value as part of the text alternative in the following manner: | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: take or leave. "as part of the text alternative" kinda makes it sound like you're overriding how this returned value would be included in the overall text alternative computation... I think the sentence stands without that clause, but feel free to keep it and resolve this comment if you disagree.
Suggested change
|
||||||
<ol> | ||||||
<li id="comp_embedded_control_textbox"><em>Textbox:</em> If the embedded control has role <a class="role-reference" href="#textbox">textbox</a>, return its value.</li> | ||||||
<li id="comp_embedded_control_combobox_or_listbox"> | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"user-adjustable" doesn't account for an embedded
readonly
field.Do we care about this?
Will the new language, the (admittedly contrived) label above would be " Flash the screen times."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I guess the old text doesn't account for
readonly
fields either.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"user-perceivable" perhaps?
Or just remove that adjective?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: This new proposed language would bring in
disabled
fields too, but I think that'd be expected if a disabled control were inside a label. What do you all think about this (also contrived) example?