wcag2.0

I seem to be having troubles getting a screen reader to read simple tables. I have the HTML below: <table alt="Account Information"> <tr> <th scope='row'>Account Number:</th> <td>1111 1111 1111</td> <td>&nbsp&nbsp<td/> <th scope='row'>Reference Number:</th> <td>XXXX XXXX XXXX</td> </tr> </table> When the screen reader hits this table it says "Table. 0 Columns. 0 Rows." I have tried many examples online and tried to use that WCAG2.0 standards as a guide line, but it doesnt seem to work. I have also tried different table layouts and structures and still get the same result. I haven't run this

In striving for WCAG 2.0 Compliance, I'm finding quite a bit of varied information regarding proper treatment of buttons, specifically what is required to consider the button accessible and compliant. What is the appropriate way to mark-up a <button> ? What attributes or combination do they need to have? My buttons fall into three categories: Buttons that have text that describes their intended action. (e.g. "Learn More" to launch a modal with more product information) Buttons that have text that does not describe their action. (e.g. "X" or text that titles a section of accordion content)

I'm developing an app with Angular and Semantic-UI . The app should be accessible, this means it should be compliant with WCAG 2.0. To reach this purpose the modals should keep focus within the dialog and prevents users from going outside or move with "tabs" between elements of the page that lays under the modal. I have found some working examples, like the following: JQuery dialog: https://jqueryui.com/dialog/#modal-confirmation dialog HTML 5.1 element: https://demo.agektmr.com/dialog ARIA modal dialog example: http://w3c.github.io/aria-practices/examples/dialog-modal/dialog.html (that I have

We are redesigning our website and there are some concerns internally that accessibility affects the design element. A toggle mode was suggested. Our standard version would still be accessible with the exception of contrast ratio and larger font size, which would be made available when you toggle to accessible mode. Has anyone had any experience with this? WCAG 2.0 allows a conforming alternate version (under some conditions ): For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided.