Jump to content

Search the Community

Showing results for tags 'Accessibility'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • W3Schools
    • General
    • Suggestions
    • Critiques
  • HTML Forums
    • HTML/XHTML
    • CSS
  • Browser Scripting
    • JavaScript
    • VBScript
  • Server Scripting
    • Web Servers
    • Version Control
    • SQL
    • ASP
    • PHP
    • .NET
    • ColdFusion
    • Java/JSP/J2EE
    • CGI
  • XML Forums
    • XML
    • XSLT/XSL-FO
    • Schema
    • Web Services
  • Multimedia
    • Multimedia
    • FLASH

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Languages

Found 3 results

  1. hi. a blind it student doing a web based audio space invaders game for the blind. pulled different bits of code from different tutorials to learn. now, need some mentoring. if any javascript or scripting gurus here, need your help. have done the code, but not sure if it is right, can some one help me out and take a look, then show me a better way to do things. then i then need to go and find a mespeak.js speech api, and then some more human voices, and see if i can find a tutorial. about how to speak out the objects on the screen, and also then just need multiplayer, regions area, updates, and
  2. I love the way W3Schools provides "Browser Support" information for HTML and CSS references! That feature has been invaluable as the development projects I'm on move to HTML 5. The move to HTML 5 is also including a better focus on Web Content Accessibility. Over the last year or so I've started to wish that you had a similar support feature with respect to Screen Readers. I know that this gets complicated very quickly due to the fact that most screen readers operate on particular OS's, and in conjunction with whatever browser (and browser version) the user prefers, but still a very basic
  3. Hi,While testing the table (pls see below) in Jaws, noticed that Jaws didn't recognize the Header 2 and the cells related to this header.Do I have to treat this table as a complex table with headers and ids?Before, I was pretty sure that rowgroup and colgroup values should help improve accessibility in this kind of tables. Maybe, it is because different screen reader tools work differently.PLs advice.Thank you!<table><caption>Table's caption</caption><tr> <th scope="col">Header 1</th> <th scope="col">Header 2</th> </tr>
×
×
  • Create New...