Skip to content

Check 508 Compliance #18

Check 508 Compliance

Check 508 Compliance #18

Manually triggered January 7, 2025 18:55
Status Success
Total duration 21s
Artifacts

check_508_compliance.yml

on: workflow_dispatch
Compliance Check
15s
Compliance Check
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Compliance Check
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
Compliance Check
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).