Skip to content

Commit c47fe58

Browse files
MissBrandyLeaMissBrandyLea
authored
Merge pull request #47 from hackforla/MissBrandyLea-patch-1
Create Link to document.md
2 parents 53717ba + c2ffd00 commit c47fe58

23 files changed

Lines changed: 2807 additions & 0 deletions

‎docs/known-issues-and-solutions/solutions-index/Link to Excel spreadsheet.md‎

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
# Alert - Link to Excel spreadsheet
2+
- WAVE Category: Alert
3+
- WAVE Alert: Link to Excel spreadsheet
4+
5+
## Page Content Status
6+
- [X] WAVE Error guidance text
7+
- [ ] Example of a DOM Snippet Generated From WAVE Tool
8+
- Project Team Error guidance
9+
- [ ] Project Team Page Details
10+
- [ ] Project Team Issue and PR details
11+
- [ ] Project Team Solution
12+
- [ ] Credits/Authors
13+
14+
## WAVE Guidance
15+
16+
WAVE Tool's Reference material on Link to Excel spreadsheet may not specifically address your problem. We provide it here for optional reading.
17+
18+
??? Info "Click to see WAVE Tool Reference"
19+
20+
This content added 2026-04-07. Check for updated guidance at: <a href="https://wave.webaim.org/api/docs?format=html#link_excel" target="_blank">https://wave.webaim.org/api/docs?format=html#link_excel</a>
21+
22+
> ### WAVE Category
23+
> Alerts
24+
> ### WAVE Error
25+
> Link to Excel spreadsheet
26+
> ### What It Means
27+
> A link to a Microsoft Excel spreadsheet is present.
28+
> ### Why It Matters
29+
> Unless authored with accessibility in mind, Microsoft Excel spreadsheets often have accessibility issues. Additionally, Excel documents are typically viewed using a separate application, and can thus cause confusion and navigation difficulties.
30+
> ### What To Do
31+
> Ensure the Excel spreadsheet is natively accessible. Additionally, inform the user that the link will open an Excel spreadsheet. Because Excel spreadsheets have limitations in accessibility (particularly for complex content) and require a separate program, HTML content should usually be used in place of or in addition to the Excel spreadsheet.
32+
> ### The Algorithm... in English
33+
> A link to a .xls or .xlsx file is present.
34+
> ### Standards and Guidelines
35+
> None
36+
37+
## Example of a DOM Snippet Generated From WAVE Tool
38+
39+
> ```html
40+
> [HTML snippet showing the problematic code structure that WAVE detected]
41+
> ```
42+
43+
44+
## Project Team Error guidance
45+
46+
The following material covers how the Project Team has provided a solution to the Link to Excel spreadsheet WAVE Alert.
47+
48+
### Project Page Details
49+
- Project Page name: [INSERT PAGE NAME or "ALL"]
50+
- Project Dev URL: [INSERT URL or "N/A"]
51+
- Requires sign in: [TRUE OR FALSE]
52+
- Required User Role: [INSERT ONE OF: Visitor, Logged in user, Admin, Security Admin]
53+
- Can access page directly from URL: [TRUE OR FALSE]
54+
- Accepts URL parameters: [TRUE OR FALSE]
55+
56+
### Project Team Issue and PR details
57+
- Related GitHub Issue(s):
58+
- [INSERT ISSUE URL]
59+
- Related Pull Request(s):
60+
- [INSERT PR URL]
61+
- React Component(s)
62+
- [INSERT PATH: e.g. path/to/Component.jsx]
63+
64+
### Project Team Solution
65+
66+
#### What is the specific problem that was occurring?
67+
<!-- Author Instructions: Add a detailed explanation of the specific accessibility problem, including context about when/where it occurs, what elements are involved, and why it's problematic for assistive technology users -->
68+
[INSERT CONTENT]
69+
70+
#### What is the proposed solution to this problem?
71+
<!-- Author Instructions: Add a few sentences describing the fix. "Why the Fix Works" comes later (see below). If there are lots of instructions required to explain the solution, include them in Developer Resources below -->
72+
[INSERT CONTENT]
73+
74+
#### Step-By-Step Guide
75+
<!-- Author Instructions: Replace details dropdown with N/A if this does not apply -->
76+
77+
??? Info "Click to see step-by-step guide"
78+
79+
[ADD DETAILED INSTRUCTIONS HERE]
80+
81+
#### Other Technical Details
82+
<!-- Author Instructions: Write N/A if this does not apply -->
83+
84+
??? Info "Click to see other technical details"
85+
86+
[INSERT OTHER DETAILS e.g. Prop References, Return Value ]
87+
88+
#### Code Snippet With Solution
89+
??? Info "Click to see code snippets"
90+
91+
[INSERT PATH file/path/to/Snippet.jsx]
92+
93+
```jsx
94+
[Code example showing the fix/solution]
95+
```
96+
97+
#### Why the Fix Works
98+
<!-- Author Instruction: Add an explanation of how the code changes resolve the accessibility issue and why this approach was chosen -->
99+
[INSERT CONTENT]
100+
101+
#### Where this solution is applicable
102+
<!-- Author Instruction: Add a bullet point list of scenarios that might trigger this error and would be fixed by applying the provided solution, e.g. particular groupings of html elements, user interactivity, code-specific edge cases -->
103+
- [INSERT SCENARIO 1]
104+
- [INSERT SCENARIO 2]
105+
- [INSERT SCENARIO N]
106+
107+
#### Screenshots of WAVE Error
108+
109+
<!-- Author Instructions: when including markdown images, ensure they are responsive by specifying EITHER width OR height. Do not provide both. -->
110+
111+
??? Info "1. Descriptive Title for Screenshot Set 1"
112+
113+
Description/text for image
114+
115+
[INSERT IMAGE HERE]
116+
117+
## Credits/Authors
118+
<!-- 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 -->
119+
- @MissBrandyLea
120+
- [INCLUDE Contributor 2]
121+
- [INCLUDE Contributor N]

‎docs/known-issues-and-solutions/solutions-index/Link to PowerPoint document.md‎

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
# Alert - Link to PowerPoint document
2+
- WAVE Category: Alert
3+
- WAVE Alert: Link to PowerPoint document
4+
5+
## Page Content Status
6+
- [X] WAVE Error guidance text
7+
- [ ] Example of a DOM Snippet Generated From WAVE Tool
8+
- Project Team Error guidance
9+
- [ ] Project Team Page Details
10+
- [ ] Project Team Issue and PR details
11+
- [ ] Project Team Solution
12+
- [ ] Credits/Authors
13+
14+
## WAVE Guidance
15+
16+
WAVE Tool's Reference material on Link to PowerPoint document may not specifically address your problem. We provide it here for optional reading.
17+
18+
??? Info "Click to see WAVE Tool Reference"
19+
20+
This content added 2026-04-07. Check for updated guidance at: <a href="https://wave.webaim.org/api/docs?format=html#link_powerpoint" target="_blank">https://wave.webaim.org/api/docs?format=html#link_powerpoint</a>
21+
22+
> ### WAVE Category
23+
> Alerts
24+
> ### WAVE Error
25+
> Link to PowerPoint document
26+
> ### What It Means
27+
> A link to a Microsoft PowerPoint presentation is present.
28+
> ### Why It Matters
29+
> Unless authored with accessibility in mind, PowerPoint documents often have accessibility issues. Additionally, PowerPoint documents are typically viewed using a separate application, and can thus cause confusion and navigation difficulties.
30+
> ### What To Do
31+
> Ensure the PowerPoint presentation is natively accessible. Additionally, inform the user that the link will open a PowerPoint document. Because PowerPoint documents have limitations in accessibility (particularly for complex content) and require a separate program, HTML content or an alternative accessible version (e.g., tagged PDF) should usually be used in place of or in addition to the PowerPoint presentation.
32+
> ### The Algorithm... in English
33+
> A link to a .ppt, .pptx, .pps, or .ppsx file is present.
34+
> ### Standards and Guidelines
35+
> None
36+
37+
## Example of a DOM Snippet Generated From WAVE Tool
38+
39+
> ```html
40+
> [HTML snippet showing the problematic code structure that WAVE detected]
41+
> ```
42+
43+
44+
## Project Team Error guidance
45+
46+
The following material covers how the Project Team has provided a solution to the Link to PowerPoint document WAVE Alert.
47+
48+
### Project Page Details
49+
- Project Page name: [INSERT PAGE NAME or "ALL"]
50+
- Project Dev URL: [INSERT URL or "N/A"]
51+
- Requires sign in: [TRUE OR FALSE]
52+
- Required User Role: [INSERT ONE OF: Visitor, Logged in user, Admin, Security Admin]
53+
- Can access page directly from URL: [TRUE OR FALSE]
54+
- Accepts URL parameters: [TRUE OR FALSE]
55+
56+
### Project Team Issue and PR details
57+
- Related GitHub Issue(s):
58+
- [INSERT ISSUE URL]
59+
- Related Pull Request(s):
60+
- [INSERT PR URL]
61+
- React Component(s)
62+
- [INSERT PATH: e.g. path/to/Component.jsx]
63+
64+
### Project Team Solution
65+
66+
#### What is the specific problem that was occurring?
67+
<!-- Author Instructions: Add a detailed explanation of the specific accessibility problem, including context about when/where it occurs, what elements are involved, and why it's problematic for assistive technology users -->
68+
[INSERT CONTENT]
69+
70+
#### What is the proposed solution to this problem?
71+
<!-- Author Instructions: Add a few sentences describing the fix. "Why the Fix Works" comes later (see below). If there are lots of instructions required to explain the solution, include them in Developer Resources below -->
72+
[INSERT CONTENT]
73+
74+
#### Step-By-Step Guide
75+
<!-- Author Instructions: Replace details dropdown with N/A if this does not apply -->
76+
77+
??? Info "Click to see step-by-step guide"
78+
79+
[ADD DETAILED INSTRUCTIONS HERE]
80+
81+
#### Other Technical Details
82+
<!-- Author Instructions: Write N/A if this does not apply -->
83+
84+
??? Info "Click to see other technical details"
85+
86+
[INSERT OTHER DETAILS e.g. Prop References, Return Value ]
87+
88+
#### Code Snippet With Solution
89+
??? Info "Click to see code snippets"
90+
91+
[INSERT PATH file/path/to/Snippet.jsx]
92+
93+
```jsx
94+
[Code example showing the fix/solution]
95+
```
96+
97+
#### Why the Fix Works
98+
<!-- Author Instruction: Add an explanation of how the code changes resolve the accessibility issue and why this approach was chosen -->
99+
[INSERT CONTENT]
100+
101+
#### Where this solution is applicable
102+
<!-- Author Instruction: Add a bullet point list of scenarios that might trigger this error and would be fixed by applying the provided solution, e.g. particular groupings of html elements, user interactivity, code-specific edge cases -->
103+
- [INSERT SCENARIO 1]
104+
- [INSERT SCENARIO 2]
105+
- [INSERT SCENARIO N]
106+
107+
#### Screenshots of WAVE Error
108+
109+
<!-- Author Instructions: when including markdown images, ensure they are responsive by specifying EITHER width OR height. Do not provide both. -->
110+
111+
??? Info "1. Descriptive Title for Screenshot Set 1"
112+
113+
Description/text for image
114+
115+
[INSERT IMAGE HERE]
116+
117+
## Credits/Authors
118+
<!-- 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 -->
119+
- @MissBrandyLea
120+
- [INCLUDE Contributor 2]
121+
- [INCLUDE Contributor N]

‎docs/known-issues-and-solutions/solutions-index/Link to Word document.md‎

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
# Alert - Link to Word document
2+
- WAVE Category: Alert
3+
- WAVE Alert: Link to Word document
4+
5+
## Page Content Status
6+
- [X] WAVE Error guidance text
7+
- [ ] Example of a DOM Snippet Generated From WAVE Tool
8+
- Project Team Error guidance
9+
- [ ] Project Team Page Details
10+
- [ ] Project Team Issue and PR details
11+
- [ ] Project Team Solution
12+
- [ ] Credits/Authors
13+
14+
## WAVE Guidance
15+
16+
WAVE Tool's Reference material on Link to Word document may not specifically address your problem. We provide it here for optional reading.
17+
18+
??? Info "Click to see WAVE Tool Reference"
19+
20+
This content added 2026-04-07. Check for updated guidance at: <a href="https://wave.webaim.org/api/docs?format=html#link_word" target="_blank">https://wave.webaim.org/api/docs?format=html#link_word</a>
21+
22+
> ### WAVE Category
23+
> Alerts
24+
> ### WAVE Error
25+
> Link to Word document
26+
> ### What It Means
27+
> A link to a Microsoft Word document is present.
28+
> ### Why It Matters
29+
> Unless authored with accessibility in mind, Microsoft Word documents often have accessibility issues. Additionally, Word documents are typically viewed using a separate application, and can thus cause confusion and navigation difficulties.
30+
> ### What To Do
31+
> Ensure that the Word document is natively accessible. Additionally, inform the user that the link will open a Word document. Because Word documents have limitations in accessibility (particularly for complex content) and require a separate program, HTML content should usually be used in place of or in addition to the Word document.
32+
> ### The Algorithm... in English
33+
> A link to a .doc or .docx file is present.
34+
> ### Standards and Guidelines
35+
> None
36+
37+
## Example of a DOM Snippet Generated From WAVE Tool
38+
39+
> ```html
40+
> [HTML snippet showing the problematic code structure that WAVE detected]
41+
> ```
42+
43+
44+
## Project Team Error guidance
45+
46+
The following material covers how the Project Team has provided a solution to the Link to Word document WAVE Alert.
47+
48+
### Project Page Details
49+
- Project Page name: [INSERT PAGE NAME or "ALL"]
50+
- Project Dev URL: [INSERT URL or "N/A"]
51+
- Requires sign in: [TRUE OR FALSE]
52+
- Required User Role: [INSERT ONE OF: Visitor, Logged in user, Admin, Security Admin]
53+
- Can access page directly from URL: [TRUE OR FALSE]
54+
- Accepts URL parameters: [TRUE OR FALSE]
55+
56+
### Project Team Issue and PR details
57+
- Related GitHub Issue(s):
58+
- [INSERT ISSUE URL]
59+
- Related Pull Request(s):
60+
- [INSERT PR URL]
61+
- React Component(s)
62+
- [INSERT PATH: e.g. path/to/Component.jsx]
63+
64+
### Project Team Solution
65+
66+
#### What is the specific problem that was occurring?
67+
<!-- Author Instructions: Add a detailed explanation of the specific accessibility problem, including context about when/where it occurs, what elements are involved, and why it's problematic for assistive technology users -->
68+
[INSERT CONTENT]
69+
70+
#### What is the proposed solution to this problem?
71+
<!-- Author Instructions: Add a few sentences describing the fix. "Why the Fix Works" comes later (see below). If there are lots of instructions required to explain the solution, include them in Developer Resources below -->
72+
[INSERT CONTENT]
73+
74+
#### Step-By-Step Guide
75+
<!-- Author Instructions: Replace details dropdown with N/A if this does not apply -->
76+
77+
??? Info "Click to see step-by-step guide"
78+
79+
[ADD DETAILED INSTRUCTIONS HERE]
80+
81+
#### Other Technical Details
82+
<!-- Author Instructions: Write N/A if this does not apply -->
83+
84+
??? Info "Click to see other technical details"
85+
86+
[INSERT OTHER DETAILS e.g. Prop References, Return Value ]
87+
88+
#### Code Snippet With Solution
89+
??? Info "Click to see code snippets"
90+
91+
[INSERT PATH file/path/to/Snippet.jsx]
92+
93+
```jsx
94+
[Code example showing the fix/solution]
95+
```
96+
97+
#### Why the Fix Works
98+
<!-- Author Instruction: Add an explanation of how the code changes resolve the accessibility issue and why this approach was chosen -->
99+
[INSERT CONTENT]
100+
101+
#### Where this solution is applicable
102+
<!-- Author Instruction: Add a bullet point list of scenarios that might trigger this error and would be fixed by applying the provided solution, e.g. particular groupings of html elements, user interactivity, code-specific edge cases -->
103+
- [INSERT SCENARIO 1]
104+
- [INSERT SCENARIO 2]
105+
- [INSERT SCENARIO N]
106+
107+
#### Screenshots of WAVE Error
108+
109+
<!-- Author Instructions: when including markdown images, ensure they are responsive by specifying EITHER width OR height. Do not provide both. -->
110+
111+
??? Info "1. Descriptive Title for Screenshot Set 1"
112+
113+
Description/text for image
114+
115+
[INSERT IMAGE HERE]
116+
117+
## Credits/Authors
118+
<!-- 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 -->
119+
- @MissBrandyLea
120+
- [INCLUDE Contributor 2]
121+
- [INCLUDE Contributor N]

0 commit comments

Comments
 (0)