Skip to content

Commit 609c65a

Browse files
authored
Update test-file.md
1 parent a6e3899 commit 609c65a

1 file changed

Lines changed: 26 additions & 21 deletions

File tree

docs/known-issues-and-solutions/solutions-index/test-file.md

Lines changed: 26 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -22,28 +22,28 @@ WAVE Tool's Reference material on Orphaned form label may not specifically addre
2222

2323
<!-- Note For Wiki Author: WAVE Tool text content will use text that break markdown generation for the details dropdown. If the copy/pasted text includes angle brackets, surround them with backticks to avoid this problem. -->
2424

25-
> ### WAVE Category
26-
> Alerts
27-
> ### WAVE Error
28-
> Layout table
29-
> ### What It Means
30-
> A layout table is present.
31-
> ### Why It Matters
32-
> Layout tables exist merely to position content visually - to create columns, insert spacing, or align content neatly for sighted users. Their content is not at all tabular in nature. Layout tables should not be used in HTML5. They can introduce reading and navigation order issues. Screen readers may interpret them as data tables (i.e., announcing column and row numbers), especially if they contain table header (`<th>`) cells. This introduces significant overhead on screen reader users.
33-
> ### What To Do
34-
> In almost every case, layout tables can be replaced with other HTML elements and styled with CSS to achieve the desired visual presentation. If the table contains tabular data, provide appropriate header (`<th>`) cells. If the layout table remains, verify that the reading and navigation order of table content (based on underlying source code order) is logical and give it role="presentation" to ensure it is not identified as a table to screen reader users.
35-
> ### The Algorithm... in English
36-
> A `<table>` element is present that does not contain any header (`<th>`) cells.
37-
> ### Standards and Guidelines
38-
> - [1.3.1 Info and Relationships (Level A)](https://webaim.org/standards/wcag/checklist#sc1.3.1)
39-
> - [1.3.2 Meaningful Sequence (Level A)](https://webaim.org/standards/wcag/checklist#sc1.3.2)
25+
### WAVE Category
26+
Alerts
27+
### WAVE Error
28+
Layout table
29+
### What It Means
30+
A layout table is present.
31+
### Why It Matters
32+
Layout tables exist merely to position content visually - to create columns, insert spacing, or align content neatly for sighted users. Their content is not at all tabular in nature. Layout tables should not be used in HTML5. They can introduce reading and navigation order issues. Screen readers may interpret them as data tables (i.e., announcing column and row numbers), especially if they contain table header (`<th>`) cells. This introduces significant overhead on screen reader users.
33+
### What To Do
34+
In almost every case, layout tables can be replaced with other HTML elements and styled with CSS to achieve the desired visual presentation. If the table contains tabular data, provide appropriate header (`<th>`) cells. If the layout table remains, verify that the reading and navigation order of table content (based on underlying source code order) is logical and give it role="presentation" to ensure it is not identified as a table to screen reader users.
35+
### The Algorithm... in English
36+
A `<table>` element is present that does not contain any header (`<th>`) cells.
37+
### Standards and Guidelines
38+
- [1.3.1 Info and Relationships (Level A)](https://webaim.org/standards/wcag/checklist#sc1.3.1)
39+
- [1.3.2 Meaningful Sequence (Level A)](https://webaim.org/standards/wcag/checklist#sc1.3.2)
4040

4141

4242
## Example of a DOM Snippet Generated From WAVE Tool
4343

44-
> ```html
45-
> [HTML snippet showing the problematic code structure that WAVE detected]
46-
> ```
44+
```html
45+
[HTML snippet showing the problematic code structure that WAVE detected]
46+
```
4747

4848

4949
## Project Team Error guidance
@@ -116,11 +116,16 @@ The following material covers how the Project Team has provided a solution to th
116116

117117
<!-- Author Instructions: when including markdown images, ensure they are responsive by specifying EITHER width OR height. Do not provide both. -->
118118

119-
<details><summary>1. [Descriptive Title for Screenshot Set 1]</summary>
119+
??? Info "1. [Descriptive Title for Screenshot Set 1]"
120120

121-
[INSERT IMAGE HERE]
121+
Description/text for image
122+
123+
![Image](https://github.com/user-attachments/assets/a61292ba-4212-403f-9583-212e0f4314e1)
124+
125+
Description/text for image
126+
127+
<img width="240" height="240" alt="image" src="https://github.com/user-attachments/assets/6470b47a-199d-4075-9cee-5337cd8af11d" />
122128

123-
</details>
124129

125130
## Credits/Authors
126131
<!-- Author Instructions: Add bullet points with GitHub handles of all HfLA members who contributed to this wiki page and/or contributed to Pull Requests that provided solutions for this page -->

0 commit comments

Comments
 (0)