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.

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

"Heading has non-empty accessible name" [ffd0e9]: Update from TF survey #2077

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

ChrisLoiselle
Copy link
Collaborator

Per review of survey heading non-empty task force conclusions, edited the following:

  • Pass ex 3, have the acc name be consistent with the text
  • Set 1.3.1 as a secondary requirement
  • Removed sentence on accessible name spec not being clear on whitespace
  • Removed inapp example 1

Per review of survey heading non-empty task force conclusions, edited the following:
* Pass ex 3, have the acc name be consistent with the text						
* Set 1.3.1 as a secondary requirement						
* Removed sentence on accessible name spec not being clear on whitespace						
* Removed inapp example 1
_rules/heading-non-empty-accessible-name-ffd0e9.md Outdated Show resolved Hide resolved
Comment on lines -176 to -180
There is no [semantic][semantic role] `heading` element.

```html
<div></div>
```
Copy link
Collaborator

Choose a reason for hiding this comment

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

Removing this example breaks our own "test case design" guidelines of Test every condition 🤔

Copy link
Member

Choose a reason for hiding this comment

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

@Jym77 We felt this was not a useful test case, so we're thinking of leaving things like this out. Is that OK with you? Happy to update the test ever condition bit then.

Copy link
Collaborator

Choose a reason for hiding this comment

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

@WilcoFiers No strong feeling about that particular example which is, indeed, quite useless 🙂

It's more on the boundaries of things on how we decide that tests are useful or not.
From a TDD point of view, we should indeed have test cases for every condition, and since we do use the test cases to validate tools, this also sounds like a good idea from an engineering point of view.
From an "illustrate the rule to human" point of view, this is indeed a fairly useless case…

=> this tends to hint that we may want to have some test cases for the computers and only show a meaningful subset to the humans.

@ChrisLoiselle
Copy link
Collaborator Author

@WilcoFiers @kengdoj please let me know how you'd like to proceed per @Jym77 's comments.

@ChrisLoiselle
Copy link
Collaborator Author

@WilcoFiers I committed @Jym77 feedback, please let me know if there is anything else needed to push this to close / done. Thanks for all your help @Jym77 and @WilcoFiers !

@Jym77 Jym77 self-requested a review July 20, 2023 14:31
@@ -10,6 +10,8 @@ accessibility_requirements:
failed: not satisfied
passed: further testing needed
inapplicable: further testing needed
secondary_requirements:
wcag20:1.3.1: # Info and Relationships (A)
Copy link
Member

Choose a reason for hiding this comment

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

This is not the correct syntax. What you should do is replace:

  wcag20:1.3.1: # Info and Relationships (A)
    forConformance: true
    failed: not satisfied
    passed: further testing needed
    inapplicable: further testing needed

with this:

  wcag20:1.3.1: # Info and Relationships (A)
    secondary: true

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@WilcoFiers am I to update within this PR or do I need to create a new one with the desired changes you recommend per secondary requirements? Not sure if you wanted another PR on 7fb7a37 for the highlight you are mentioning in this comment here.

Copy link
Member

Choose a reason for hiding this comment

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

No please update in this PR.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@WilcoFiers when I view the file in "edit file" it shows your changes. I can't approve per admin settings, thus not sure what else to do to "close" this issue and "update the PR" from my side.

Copy link
Collaborator Author

@ChrisLoiselle ChrisLoiselle left a comment

Choose a reason for hiding this comment

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

@WilcoFiers I don't have access to approve the changes only to comment. I'll pursue updating the file and submitting the updated PR.

@Jym77 Jym77 changed the title Update-from-survey-heading-non-empty-accessible-name-changes "Heading has non-empty accessible name" [ffd0e9]: Update from TF survey Aug 10, 2023
@ChrisLoiselle
Copy link
Collaborator Author

@WilcoFiers , I see this is still open and aged quite a bit. Did you want me to take any action on this or would you like to close as no longer applicable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants