Skip to content

Commit c994393

Browse files
Merge pull request #54 from TaskarCenterAtUW/feat/docs-accessmap/3072-add-accessmap-um
Add AccessMap User Manual
2 parents e6a2f4b + cbd4e2e commit c994393

File tree

143 files changed

+2310
-156
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

143 files changed

+2310
-156
lines changed

.github/copilot-instructions.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,38 @@ cd util
135135

136136
**Why**: Navigation structure and guide indices aren't hand-maintained. These scripts parse `/docs` structure, extract frontmatter titles, and generate the Markdown files accordingly. Generation of the nav section of `zensical.toml` is done afterwards to ensure all files are included.
137137

138+
### Process Screenshots
139+
140+
The `process-screenshot.py` utility generates themed light/dark variants of screenshots with borders and drop shadows, saved as maximally-compressed lossless PNGs:
141+
142+
```powershell
143+
# Ensure venv is activated first!
144+
..\.venv\Scripts\Activate.ps1
145+
146+
# Process a single screenshot
147+
python .\util\process-screenshot.py docs\resources\images\example\screenshot.png
148+
149+
# Process all images in a directory (optionally --recurse for subdirs)
150+
python .\util\process-screenshot.py docs\resources\images\example\
151+
152+
# Apply a named custom profile
153+
python .\util\process-screenshot.py screenshot.png --profile uw-purple
154+
155+
# Regenerate existing output files
156+
python .\util\process-screenshot.py screenshot.png --overwrite
157+
```
158+
159+
**Output**: For each input `image.png`, produces `image-light.png` (dark border + shadow for light pages) and `image-dark.png` (light border + glow for dark pages). Mode-tagged sources (e.g., `image.light.png`) produce only the matching variant.
160+
161+
**Markdown usage**:
162+
163+
```markdown
164+
![Alt text](path/to/image-light.png#only-light)
165+
![Alt text](path/to/image-dark.png#only-dark)
166+
```
167+
168+
Run with `--help` for all options including per-variant color, shadow, and blur overrides.
169+
138170
### Validate Links
139171

140172
```powershell
@@ -345,5 +377,6 @@ Refer to the official Zensical documentation, which is hosted online at https://
345377
- `util/generate-nav.Tests.ps1`: Pester tests for nav generator
346378
- `util/check-links.ps1`: PowerShell validation of links (not standard CI integration)
347379
- `util/check-links.Tests.ps1`: Pester tests for link checker
380+
- `util/process-screenshot.py`: Generates themed light/dark screenshot variants with borders, shadows, and maximum lossless PNG compression
348381
- `/includes/abbreviations.md`: Global acronym definitions
349382
- `/resources/stylesheets/extra.css`: Theming
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
description: Project-wide instructions for the TCAT Wiki workspace
3+
applyTo: "**"
4+
---
5+
6+
<!-- @format -->
7+
8+
IMPORTANT: This project uses a Python virtual environment (`.venv/`). ALWAYS run `.\.venv\Scripts\Activate.ps1` before ANY terminal command (zensical, pip, python, utility scripts, etc.). Never assume the venv is already activated.

CONTRIBUTING.md

Lines changed: 34 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -192,25 +192,53 @@ For creating screenshots with a consistent style, Firefox DevTools is to be used
192192

193193
3. Add custom device profiles:
194194
1. Name: `[Screenshot] Web - Portrait`
195-
1. Size: `671`x`1196`
195+
1. Size: `810`x`1440`
196196

197197
2. Device Pixel Ratio: `1`
198198

199199
3. User Agent String: `Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0`
200200

201201
2. Name: `[Screenshot] Web - Landscape`
202-
1. Size: `1196`x`671`
202+
1. Size: `1440`x`810`
203203

204204
2. Device Pixel Ratio: `1`
205205

206206
3. User Agent String: `Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0`
207207

208-
4. Resulting screenshots will fit exactly within the 2px outside border present in the following screenshot templates:
209-
1. [Landscape (Desktop) - templates/images/screenshots/landscape-desktop.png](https://github.com/TaskarCenterAtUW/tcat-wiki/blob/main/templates/images/screenshots/landscape-desktop.png)
208+
4. It is recommended to remove all embedded metadata, such as with the use of [ExifToolGUI](https://exiftool.org/gui/).
210209

211-
2. [Portrait (Desktop) - templates/images/screenshots/portrait-desktop.png](https://github.com/TaskarCenterAtUW/tcat-wiki/blob/main/templates/images/screenshots/portrait-desktop.png)
210+
5. Process screenshots with the `process-screenshot.py` utility to generate themed light/dark variants with borders and drop shadows:
212211

213-
5. It is recommended to remove all embedded metadata, such as with the use of [ExifToolGUI](https://exiftool.org/gui/).
212+
```powershell
213+
# Ensure venv is activated first!
214+
..\.venv\Scripts\Activate.ps1
215+
216+
# Process a single screenshot
217+
python .\util\process-screenshot.py docs\resources\images\example\screenshot.png
218+
219+
# Process all images in a directory
220+
python .\util\process-screenshot.py docs\resources\images\example\
221+
222+
# Process recursively with a custom profile
223+
python .\util\process-screenshot.py docs\resources\images\ --recurse --profile uw-purple
224+
225+
# Regenerate existing output files
226+
python .\util\process-screenshot.py screenshot.png --overwrite
227+
```
228+
229+
The script produces two variants per input image, saved as maximally-compressed lossless PNGs:
230+
231+
- `{name}-light.png` — dark border + drop shadow for light theme pages
232+
- `{name}-dark.png` — light border + glow for dark theme pages
233+
234+
Reference them in Markdown with Zensical's theme-switching fragments:
235+
236+
```markdown
237+
![Alt text](path/to/image-light.png#only-light)
238+
![Alt text](path/to/image-dark.png#only-dark)
239+
```
240+
241+
Mode-tagged source files (e.g., `image.light.png`, `image.dark.png`) generate only the matching variant. Run with `--help` for all options including per-variant color/shadow overrides.
214242
215243
##### Image Annotations
216244

docs/accessmap/index.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,10 @@ title: AccessMap
66

77
## AccessMap
88

9-
AccessMap ([https://accessmap.app](https://accessmap.app)) provides detailed information in select cities on pedestrian paths, transit stations, elevation changes, curb ramps, and more to enable accessibility-focused multimodal routing.
9+
AccessMap ([accessmap.app](https://accessmap.app)) is a web app that provides detailed information in select cities on pedestrian paths, transit stations, elevation changes, curb ramps, and more to enable accessibility-focused multimodal routing.
10+
11+
![AccessMap](../resources/images/accessmap/accessmap-light.png#only-light)
12+
![AccessMap](../resources/images/accessmap/accessmap-dark.png#only-dark)
1013

1114
---
1215

@@ -18,4 +21,4 @@ _For a list of all guides on the TCAT Wiki, refer to the [Guides List](../guides
1821

1922
#### [AccessMap User Manual](user-manual/index.md)
2023

21-
This user manual explains how to use the AccessMap application.
24+
This user manual explains how to use the AccessMap web application.
Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
title: Leaving Feedback
3+
nav_order: 7
4+
tags:
5+
- Guide
6+
- External
7+
- User
8+
# exclude-from-main-guides-list
9+
---
10+
11+
<!-- @format -->
12+
13+
## Leaving Feedback
14+
15+
This section explains how to leave comments on map features to report observations and help improve the data.
16+
17+
_For a list of all guides on the TCAT Wiki, refer to the [Guides List](../../guides-list/index.md)._
18+
19+
---
20+
21+
### Overview
22+
23+
AccessMap allows you to **share feedback** about routing directions and about specific features in and around the pedestrian network, such as sidewalks, crossings, curb ramps, or landmarks.
24+
25+
Feedback helps TCAT and community contributors identify issues in the underlying pedestrian data and prioritize improvements.
26+
27+
---
28+
29+
### Feature Feedback
30+
31+
To report an issue with a specific map feature (such as a sidewalk, crossing, or curb ramp), tap or click on or near the feature to open a [details popup](interface.md#inspecting-a-feature), then select **Share Feedback**. This opens the **Share feedback about this feature** form.
32+
33+
Select one or more issue types by checking the relevant boxes:
34+
35+
| Checkbox | Use When |
36+
|:------------------------------------------|:----------------------------------------------------------------|
37+
| **The feature is located somewhere else** | The feature exists but is mapped in the wrong location |
38+
| **Inaccurate information** | An attribute is incorrect (e.g., wrong surface type or incline) |
39+
| **Add something that's missing** | A real-world feature is not represented in the data |
40+
41+
Optionally, add details in the **Comments** text field, then select **Submit** to send your feedback (or **Cancel** to dismiss).
42+
43+
![Share feedback about this feature form](../../resources/images/accessmap/user-manual/feedback/feature-popup-light.png#only-light)
44+
![Share feedback about this feature form](../../resources/images/accessmap/user-manual/feedback/feature-popup-dark.png#only-dark)
45+
46+
---
47+
48+
### Step Feedback
49+
50+
To report an issue with a specific segment of a planned route, open the [Directions panel](navigation.md#directions-panel) and select the **Share Feedback** link on any direction card. This opens the **Share feedback about this step** form.
51+
52+
Select one or more issue types by checking the relevant boxes:
53+
54+
| Checkbox | Use When |
55+
|:----------------------------------------|:-----------------------------------------------------------------|
56+
| **Inaccurate GPS** | Your GPS position does not align with the route shown on the map |
57+
| **This part of the path is inaccurate** | The described path segment does not match real-world conditions |
58+
| **Add something that's missing** | Relevant information about the step is absent |
59+
60+
Optionally, add details in the **Comments** text field, then select **Submit** to send your feedback (or **Cancel** to dismiss).
61+
62+
![Share feedback about this step form](../../resources/images/accessmap/user-manual/feedback/route-popup-light.png#only-light)
63+
![Share feedback about this step form](../../resources/images/accessmap/user-manual/feedback/route-popup-dark.png#only-dark)
64+
65+
!!! tip "Writing Effective Comments"
66+
67+
Be concise and specific. Good examples:
68+
69+
- _"This crossing does not have markings"_
70+
- _"Surface is gravel, not concrete"_
71+
- _"There is a newly installed curb ramp at this corner"_
72+
- _"There is not a bench here"_
73+
- _"The path here is blocked by a tree"_
74+
75+
---
76+
77+
### What Happens to Your Feedback
78+
79+
Comments submitted through AccessMap are collected by TCAT and used to assess data quality and guide future data corrections.
80+
81+
---
82+
83+
!!! success "Thank you for using AccessMap!"
84+
85+
---
86+
87+
Previous: [Navigation](navigation.md)
88+
89+
Return: [AccessMap User Manual](index.md)
Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: Getting Started
3+
nav_order: 2
4+
tags:
5+
- Guide
6+
- External
7+
- User
8+
# exclude-from-main-guides-list
9+
---
10+
11+
<!-- @format -->
12+
13+
## Getting Started
14+
15+
This section explains how to access AccessMap, select a region, and take the built-in tour.
16+
17+
_For a list of all guides on the TCAT Wiki, refer to the [Guides List](../../guides-list/index.md)._
18+
19+
---
20+
21+
### Accessing AccessMap
22+
23+
AccessMap is a web application, so **no download or installation is required**. It runs directly in your browser on any device, including phone, tablet, or desktop.
24+
25+
1. Open your preferred web browser (e.g., Chrome, Firefox, Safari, Edge)
26+
27+
2. Navigate to [AccessMap.app](https://accessmap.app)
28+
29+
![AccessMap landing page](../../resources/images/accessmap/user-manual/getting-started/landing-light.png#only-light)
30+
![AccessMap landing page](../../resources/images/accessmap/user-manual/getting-started/landing-dark.png#only-dark)
31+
32+
---
33+
34+
### Selecting a Region
35+
36+
AccessMap is available in a number of regions across Washington State and beyond. When you first open AccessMap, the map will be centered on the default region. To switch to a different region:
37+
38+
1. Select the **region name** displayed in a box at the top of the left sidebar (e.g., "Seattle, WA")
39+
40+
2. A **Regions** dialog will appear with a filterable list of all available regions
41+
42+
3. Scroll through or type in the **filter** field to narrow the list
43+
44+
4. Select the region you want to explore
45+
46+
![Regions dialog with filter](../../resources/images/accessmap/user-manual/getting-started/region-light.png#only-light)
47+
![Regions dialog with filter](../../resources/images/accessmap/user-manual/getting-started/region-dark.png#only-dark)
48+
49+
!!! info "Coverage"
50+
51+
AccessMap coverage depends on available pedestrian network data. Coverage outside Washington State varies by region and depends on local data availability.
52+
53+
---
54+
55+
### Taking the Tour
56+
57+
If you are new to AccessMap, select the **Take a tour** button (top right of the map) for a quick guided walkthrough of the interface. The tour opens a series of popups that highlight key features and provide an introduction to planning your first route.
58+
59+
![Tour popup](../../resources/images/accessmap/user-manual/getting-started/tour-light.png#only-light)
60+
![Tour popup](../../resources/images/accessmap/user-manual/getting-started/tour-dark.png#only-dark)
61+
62+
---
63+
64+
Previous: [AccessMap User Manual](index.md)
65+
66+
Next: [Interface Overview](interface.md)

docs/accessmap/user-manual/index.md

Lines changed: 60 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: AccessMap User Manual
3+
nav_order: 1
34
tags:
45
- User Manual
56
- External
@@ -10,10 +11,67 @@ tags:
1011

1112
## AccessMap User Manual
1213

13-
This user manual explains how to use the AccessMap application.
14+
This user manual explains how to use the AccessMap web application.
1415

1516
_For a list of all guides on the TCAT Wiki, refer to the [Guides List](../../guides-list/index.md)._
1617

1718
---
1819

19-
_Coming soon!_
20+
### About AccessMap
21+
22+
[AccessMap](https://accessmap.app) is a free, web-based pedestrian trip planner developed by the Taskar Center for Accessible Technology (TCAT) at the University of Washington. Unlike general-purpose navigation apps, AccessMap is designed to support the full diversity of how pedestrians travel — accounting for mobility aids, vision, and physical ability — and to give users meaningful control over their route.
23+
24+
AccessMap provides:
25+
26+
- **Pedestrian-specific routing** — routes on sidewalks, crossings, and footways rather than roadways
27+
- **Elevation awareness** — color-coded visualization of incline grades along paths
28+
- **Barrier and curb ramp information** — identification and optional avoidance of raised curbs and stairs
29+
- **Customizable mobility profiles** — tailored routing for manual wheelchair users, powered wheelchair users, support cane users, and blind/low-vision users, as well as a fully customizable profile
30+
- **Screen reader support** — step-by-step directions with landmark-based alerts for non-visual navigation
31+
- **Feedback** — the ability to leave comments on map features to help improve the underlying data
32+
33+
AccessMap is powered by [OpenSidewalks](../../opensidewalks/index.md) and [OpenStreetMap](https://welcome.openstreetmap.org/) data.
34+
35+
---
36+
37+
### Quick Start
38+
39+
1. **Open** your web browser and navigate to [AccessMap.app](https://accessmap.app)
40+
2. **Select** a region from the region selector in the top bar
41+
3. **Choose** a mobility profile that fits your needs, or customize your own!
42+
4. **Search** for or select a starting point and destination to plan your route
43+
44+
---
45+
46+
![AccessMap](../../resources/images/accessmap/user-manual/index/accessmap-light.png#only-light)
47+
![AccessMap](../../resources/images/accessmap/user-manual/index/accessmap-dark.png#only-dark)
48+
49+
---
50+
51+
### Table of Contents
52+
53+
AccessMap User Manual Table of Contents
54+
55+
#### [Getting Started](getting-started.md)
56+
57+
This section explains how to access AccessMap, select a region, and take the built-in tour.
58+
59+
#### [Interface Overview](interface.md)
60+
61+
This section introduces the AccessMap interface, including the sidebar, map controls, and legend.
62+
63+
#### [Mobility Profiles and Preferences](profiles.md)
64+
65+
This section explains how to select a pre-defined mobility profile and how to customize individual routing preferences.
66+
67+
#### [Planning a Route](route-planning.md)
68+
69+
This section explains how to set a starting point and destination, plan a route, and read the route display.
70+
71+
#### [Navigation](navigation.md)
72+
73+
This section explains how to follow step-by-step directions and use screen reader alerts for non-visual navigation.
74+
75+
#### [Leaving Feedback](feedback.md)
76+
77+
This section explains how to leave comments on map features to report observations and help improve the data.

0 commit comments

Comments
 (0)