mirror of https://github.com/docusealco/docuseal
master
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.0.8
1.1.0
1.1.1
1.1.10
1.1.11
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.1.9
1.2.0
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.4.0
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
1.5.7
1.5.8
1.5.9
1.6.0
1.6.1
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
1.7.0
1.7.1
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.7
1.7.8
1.7.9
1.8.0
1.8.1
1.8.2
1.8.3
1.8.4
1.8.5
1.8.6
1.8.7
1.8.8
1.8.9
1.9.0
1.9.1
1.9.10
1.9.2
1.9.3
1.9.4
1.9.5
1.9.6
1.9.7
1.9.8
1.9.9
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
2.0.6
2.0.7
2.0.8
2.0.9
2.1.0
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.2.0
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9
2.3.0
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.4.0
${ noResults }
3 Commits (0828065b803e8e2ebab8c784aaf12cbc1f99491e)
| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
692341dd2d |
Add WCAG 2.1 AA full audit report and update progress plan
Consolidated findings from 4-agent parallel audit into .reports/wcag-2.1-aa-audit.md (~80 issues: 7 critical, 8 high, 11 medium, 13 minor). Updated progress plan with session summary and prioritized remediation recommendations. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
3 weeks ago |
|
|
5395a74600 |
Document architecture decision: keep direct text→HTML in pdf_text_to_html parsers
Analyzed whether emitting Markdown as an intermediate format would improve lib/pdf_text_to_html.rb and app/javascript/template_builder/pdf_text_to_html.js. Decision: no change warranted. Key reasons: no full Markdown gem on Ruby side, snarkdown is inline-only (no block elements), dir="auto" RTL support can't be expressed in Markdown, and PDF text contains raw * _ # characters that would corrupt Markdown rendering. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
3 weeks ago |
|
|
778a379086 |
Add PDF View/Text View tab switcher design report and update plan
Documents the accessibility specialist review of the proposed tab switcher feature: ARIA tablist/tab/tabpanel pattern requirements, heuristic HTML parsing strategy for extracted text, signing form UX recommendation (read-only text view + always-visible Vue panel), and concrete pitfalls including DaisyUI incompatibility with APG keyboard model, 15-page cap handling, and RTL text direction. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
3 weeks ago |