|
From: Jan N. <jan...@gm...> - 2025-10-21 07:45:27
|
Op za 18 okt 2025 om 23:07 schreef Kevin Walzer:
> 2. Jan noted that the test suite failed on all three platforms during
> automated Github runs. I added code to accessibility.tcl to return an
> empty namespace if a screen reader isn't running. That way there will be
> no unintended side effects from the accessibility commands conflicting
> with the test suite, which now runs normally on all three platforms.
> Note: I am NOT including automated testing of accessibility within the
> test suite itself. Accessibility is best tested through interactive use
> of a screen reader.
Unfortunately, testcases are still failing when there is no
screen-reader. e.g.:
==== font-1.1 TkFontPkgInit FAILED
==== Contents of test case:
interp create foo
foo eval {
load {} Tk
....
invalid command name "::tk::accessible::check_screenreader"
while executing
"::tk::accessible::check_screenreader"
invoked from within
"if {([::tk::accessible::check_screenreader] eq 0 ||
[::tk::accessible::check_screenreader] eq "")} {
# Do not load if screen reader is not running..."
(file "/Users/runner/work/tk/tk/tk/library/accessibility.tcl" line 14)
invoked from within
<https://github.com/tcltk/tk/actions/runs/18675529789/job/5324461262>
This is on Linux. but Windows and MacOS fail too
:-(
Jan Nijtmans
|