Skip to content

issues Search Results · repo:w3c/wcag2ict language:JavaScript

Filter by

361 results
 (84 ms)

361 results

inw3c/wcag2ict (press backspace or delete to remove)

In doing another round of comparison with the EN 301 549, I ve noticed a few more editorial issues: - [x] Consistent use of satisfy in all its conjugations rather than meet and its variations - [x] ...
  • maryjom
  • 1
  • Opened 
    5 days ago
  • #761

We recently made a change for another SC that had the following sentence in the middle of a note: Sets of software that meet this definition appear to be extremely rare. To make what parts of notes are ...
3.2.6 Consistent Help
Editorial
  • maryjom
  • 4
  • Opened 
    5 days ago
  • #760

We had added Note 2 from the EN 301 549 clause 10.3.1.2 but neglected to notate that this note is only applicable to non-web documents. Or is this also applicable to non-web software? This is the note: ...
3.1.2 Language of Parts
Editorial
  • maryjom
  • 1
  • Opened 
    5 days ago
  • #758

When reviewing the EN 301 549 clause 10.2.4.2 it doesn t add the note from WCAG2ICT that says: Note 2 (Added) Although not required by this success criterion, ensuring that individual windows or screens ...
2.4.2 Page Titled
Editorial
  • maryjom
  • 3
  • Opened 
    5 days ago
  • #757

EN 301 549 has an additional note on 10.1.4.4 Resize Text. This only exists for non-web documents, and does not appear for non-web software. Do we need this note? NOTE: It is best practice to use only ...
  • maryjom
  • 3
  • Opened 
    6 days ago
  • #753

The first paragraph under Applying SC 2.1.1 Keyboard to Non-Web Documents and Software only talks about non-web software. It doesn t say how this applies to non-web documents any more. This is what it ...
  • maryjom
  • 2
  • Opened 
    6 days ago
  • #752

Summary The WCAG2ICT Task Force has made updates to align guidance with EN 301 549 currently being drafted for the European Accessibility Act. This update includes a number of editorial changes as well ...
Please Review
  • maryjom
  • 4
  • Opened 
    11 days ago
  • #750

- Review markdown files. - Replace current link text with bolded link text as appropriate per WCAG2ICT minutes decision.
Editorial
Project task
  • ChrisLoiselle
  • 4
  • Opened 
    16 days ago
  • #745

@maryjom @tamsinewing555 made some editorial suggestions in #737 Would appreciate a review of these changes, and ideally a merge into main so that we can have them available for publication.
  • daniel-montalvo
  • 2
  • Opened 
    23 days ago
  • #742

It may make sense to add a precondition to 2.1.1 Keyboard, as it should only be applicable when there is an underlying platform that provides a device-independent keyboard interface service. See the discussion ...
2.1.1 Keyboard
  • maryjom
  • 4
  • Opened 
    27 days ago
  • #740
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub