Philosophy of Mind [ed: Heather Salazar]

@christina.hendricks I’ve resent invites for you to join the remaining books! While I was doing so, I noticed that this book is titled “Introduction to the Philosophy of Mind” while the others follow the pattern “Introduction to Philosophy: Ethics”. If this was a recent change, I’d suggest updating the Book Information and any other places inside the book where the full book-title is mentioned, perhaps also the book cover. This might already be on your radar, and apologies if so!

Ah, I didn’t notice this, so thank you for pointing it out! I will have to go through and try to find all the places the title is mentioned …

For mentions inside the book, you can use the Search & Replace tool! Take a look at the Pressbooks user guide chapter: Hopefully this will save time going through the book to make the replacements.

1 Like

Wow, I think there are just a couple of things left to do on this book!

  1. Accessibility Assessment: I went through and answered the questions I knew the answers to without doing a full book assessment yet.

  2. A small thing, and a question for @apurva: when I do export to PDF (whether print or digital), if I look at the “sidebar” with a ToC in my PDF reader (Preview for Mac), the organization looks strange. It looks like most things are in heading 1 and so out towards the left on the list of ToC on the sidebar, except then it appears that all of the chapter titles act like they’re heading 2 and are all organized under “Introduction to the Book,” which is the last heading 1 item before the chapters. Then the rest of the backmatter items show up as if heading one.

It’s the same on Adobe Acrobat reader, if you look at the sidebar with the “bookmark” icon clicked.

I wouldn’t worry too much about it but then it makes me wonder whether this creates an accessibility problem. The PDF would read as if each chapter were somehow nested under the larger category of “Introduction to the Book.”

Any thoughts, Apurva?

That’s very exciting! :clap:t5: Not too far before we can release!

This is a really good catch, Christina, and it does look this mis-ordering will affect the accessibility of the PDF. I did try to do some troubleshooting myself, but unfortunately couldn’t come up with a fix. So, I have been in touch with the Pressbooks team, to see if they can possibly look into this in more detail and hopefully help us find a solution. I’ll keep you posted when I hear more from them!

1 Like

Hi Christina! I’ve had a good exchange with the Pressbooks team, who have in fact compiled a comprehensive list of accessibility improvements they can make to the TOC/bookmarks navigation in the PDF exports. They will be going over this list over time, but have suggested some temporary solutions for us as follows:

  • In order for the chapters to be correctly and logically nested in the bookmarks bar in the PDF, the following changes need to be made:
    • A new part needs to be added to the book, and marked as 'Invisible’
    • The existing part on the book (titled ‘Chapters’) needs to be marked as visible
    • Note: The slight downside of this change is that the webbook version will display the visible part (titled ‘Chapters’) in the TOC, which I know was something we hoped to avoid. We could, if desired, implement these changes to export a PDF and ‘pin’ this file so it is available for downloads (As long as this file is the most recently exported PDF file, it will appear in the Book Downloads dropdown on the homepage.). Then, we could revert the changes and export the ebook and any other formats, so the web version is similar to how it is now. I’ll leave it to you whether you’d like to do multiple exports (one for PDF and one for the other formats) as Pressbooks has suggested, or whether to just implement the changes and let this remain the same across the formats.
    • If necessary, you can also remove the automatic part and chapter numbering on the book globally, so that export formats do not contain a part-title page or a part-number in the TOC. If you wanted to preserve the chapter numbers, you will need to add these in manually, (in the chapter-title), OR leave the automatic part and chapter numbering option enabled. You can decide on whether to enable/disable the auto chapter and part numbering, and enter this manually.
  • In order for the chapter endnotes to not appear in the bookmarks bar in PDF, these will need to be reset to regular footnotes. Go to Appearance --> Theme Options --> PDF Options --> Footnote Style --> Select ‘Regular Footnote’ and Save. Please feel free to implement this change if you would like to.
  • For the title page: with the current Custom Title page, the only solution is to remove this page from displaying in the bookmarks bar entirely, which may not be best practice. I can provide some instructions (or implement some changes) so that the page styling remains the same, but it does not display in the bookmarks bar in PDF. If we decide to go with this, it may be worth mentioning a few sentences about this in the Accessibility Statement. Alternatively, we could revert to the regular auto-generation Title Page, which should display correctly in the bar. Please let me know which of the 2 options you prefer.
  • Unfortunately, the copyright page is not listed in the bookmarks bar in the PDF. There’s no short term solution for this, but I wanted to flag this if you wanted to include it in the Accessibility Assessment.

I’ve tried to list out all the major decisions/action items in bold formatting above. If there’s anything that still unclear or confusing, please let me know. This issue has turned to be a bit more complex than expected, so I’m happy to explain things in more detail or answer any outstanding questions that you might have.

Thank you for this comprehensive info, @apurva . I think I understand nearly all of it, but I have a question about this part:

I get that the existing part needs to be marked as visible and I’ll think about whether to keep it that way forever or just for the PDF export. But I am not sure I understand the first bullet, above–is it that I just need to add an empty part somewhere in the book and make it invisible? Does it matter where it goes?

As for the custom title page, I think for accessibility purposes it’s best to keep it in the bookmarks bar rather than removing it. So I guess for now that means taking out the custom title page. My understanding is that if I just remove the custom one then one will be auto-generated in its place and work correctly for the PDF bookmarks bar. Please let me know if that isn’t correct, though.

I’ll change the footnotes now!

Oh, a couple of other question about accessibility, @apurva:

  1. I’m doing the accessibility checklist and I want to double check that the headings should start with heading 2, in the body of the chapters or frontmatter/backmatter. I believe the chapter title (or frontmatter/backmatter title) is in heading 1, so headings after that should start with heading 2, but I want to make sure that’s correct. That’s how we have it now!

  2. The checklist asks about things for tables that I can’t figure out for the table on the accessibility checklist itself, which is done through TablePress.

  • First, it asks about row and column headers, and I think it only has column headers. Is that your read too?
  • It also asks about a caption, and I can’t figure out how to do that on TablePress (there is an option for the table title to appear above or below the table…do you think that serves the same point as a caption?)
  • Finally, it asks about cell padding and I don’t know how to tell what that is on a TablePress table.

I’m now wondering if it’s better to just create a table within Pressbooks itself as perthe tables chapter in the BCcampus accessibility toolkit? Then I could manipulate the html or follow the other manual instructions for Pressbooks there.


Yep, all that’s needed is to add an empty part in the book and mark it as invisible. I don’t think order matters. When I tested this solution, I placed this empty invisible part after the ‘Chapters’ one, and it seemed to work well.

Yes, that’s right!

Sounds good, thanks so much. :slight_smile:

And for these questions on accessibility:

  1. Yes, that’s right! Since the chapter titles are styled as heading 1, anything that follows should start with heading 2, and go lower.
  2. Looking at the webbook checklist table, it looks like there are table rows, however, these have not been identified using the scope method outlined in the BCcampus Accessibility Toolkit. A caption can added if you enable the “Print Table Description” option. And as for the cell padding – there’s at minimum, a uniform padding of 8px in each cell.

Given that there doesn’t appear to be a simple way to add table row headers using TablePress, I’d say yes, creating the tables using HTML may be best. Apologies for asking you to redo these tables – but it’s better that this be resolved now rather than later!

Argh: so sorry, @christina.hendricks, I completely fell off the map on this project. My apologies!

I’m not sure where things are now, or if I can still help in some way. I’m looking back through the messages, but am not clear on what’s been done/still needed. If there is something I could help with, please call on me!

Hi @xolotl–thanks for checking back in!
If you have time, it would be really great if you could help with the last little bit.

The last thing to do is to redo the tables as per the accessibility concerns listed above. There are two tables: accessibility checklist and version history. They are currently in TablePress, but they need to be redone in html as per the tables chapter in the BCcampus accessibility toolkit.

Then I think we can fill out the accessibility checklist with a “yes” for all the parts about tables and we’ll be ready to go.

Please let me know if you could do this, and if so, whether it might be within the next few days. I can get to it in the next few days if not!

1 Like

I can help with that @christina.hendricks! I will take a look at the tables tonight.

1 Like

@christina.hendricks @apurva: As a first step, I reformatted the table in the version history page to follow the BCCcampus accessible toolkit table standards.

Before I do the other, we should resolve some questions:

  1. The caption is redundant to the header right before the table, but the default styles here place the caption below the table, so I left both. It’s a bit redundant, but it seems like both the title and caption might be warranted, right?
  2. I styled the table in the “full grid” PB standard style which seems most visually clear, but other standard PB table styles are available. Is full grid the right choice?

For the accessibility assessment table on the other page, we have a bit of a conundrum as it includes row headers that apply to multiple rows, but according to accessibility standards, we should not merge cells or probably leave cells blank. The most accessible thing to do seems to be to repeat the row headers for every row, which may seem a bit redundant. Do you all agree?

Lastly, these accessible tables won’t have the sorting, searching and row display controls that come via TablePress, but these small tables don’t really seem to need them. That might be less true in books with larger data tables.

Thanks for getting this going, Nate!

Hmm, looking at the table for the version history, I’d say the heading above it is not necessary, but the caption should remain as is.

I find this to be the clearest too! Happy to let Christina chime in if she prefers another table.

Hmm, repeating the row headers does seem to be the best route. It will not seem redundant for anyone reading the book with a screen reader, and if anything, will also make it much clearer for those reading the book in other formats (eg: if you’re scrolling through the table, sometimes the header row is off-screen, so it may not be easiest to recall what it was).

Agreed about the search and sort display controls as being less of a need for these small tables!

Thanks so much, @xolotl for working on this! I agree with @apurva on her comments above. I am not sure what the other table styles in PB look like, but this one looks fine. And I think the issue with the row headers is best addressed by repeating the headers for each row where needed. I don’t know exactly what the best approach is for a table like this is from an accessibility perspective, but if we find out more later we can change it.

1 Like

@christina.hendricks – could you let me know when all of these final changes have been completed? I’m hoping to confirm the final PDF page count to calculate the size for the cover for the print format. I can then pass this info along to Jonathan, who’s working on the cover design to finalize this too!

Sure thing, @apurva. I think once @xolotl finishes the table then that’s it. We can generate the exports and make them visible on the site and hit “publish”!

1 Like

OK, I updated the Accessibility Checklist table to be accessible, but kept the header in this case as it’s so far from the caption.

1 Like

Thanks, Nate!

@apurva, we’re just about ready to publish. I was going to do the exports and realized the export page has a list of “supported formats” and “other formats.” Should I do exports in all of them? In the Introduction to the Series section we do talk about some of the “other formats,” like PB and WP XML, open office, and common cartridge. So I’m guessing I should export in all of the formats?

I did export in all of the supported formats, so you should have the PDF page count now (looks like 97). And the ToC on the PDF looks good to me now!